Search results for "Solution architecture"
showing 6 items of 6 documents
PASSI: Process for Agent Societies Specification and Implementation
2014
PASSI (a Process for Agent Societies Specification and Implementation) is a step-by-step requirement-to-code methodology for designing and developing multiagent societies, integrating design models and concepts from both Object-Oriented software engineering and artificial intelligence approaches using the UML notation. The models and phases of PASSI encompass anthropomorphic representation of system requirements, social viewpoint, solution architecture, code production and reuse, and deployment configuration supporting mobility of agents. PASSI is made up of five models, concerning different design levels, and 12 activities performed to build multiagent systems. In PASSI, the UML notation i…
Fifth Generation Networking Principles for a Service Driven Future Internet Architecture
2010
Published version of an article published in Wireless Personal Communications, vol. 57:393-411. Also available from the publisher at: http://dx.doi.org/10.1007/s11277-010-0076-7 The vision of all-IP networks where IP forms the simple common layer understandable across the whole network has undeniable advantages. However, such simplicity comes as a major hurdle to flexibility and functionality to the architecture. This is evident from the increasingly numerous and complex engineering solutions and optimizations required to accommodate essential qualities like mobility, security, realtime communication support etc or to mitigate the shortcomings inherent in the 'traditional Internet' architec…
Systemic Management of Architectural Decisions in Enterprise Architecture Planning. Four Dimensions and Three Abstraction Levels
2006
This paper presents a process model for the management of architectural decisions in enterprise architecture planning. First, decisions are made at the enterprise level, with strategic business considerations on the enterprise information, systems and technology strategy and governance issues. The next step is to define the domains, to then go on with domain architecture decisions. At the systems level, the enterprise and domain architecture decisions are collected and converted into architecture descriptions accurate in precision, form and detail to be given as input to the information systems development process, following the architectural planning. The model is derived from previous wor…
Business architecture development at public administration - Insights from government EA method engineering project in Finland
2008
Governments worldwide are concerned for efficient production of services to customers. To improve quality of services and to make service production more efficient, information and communication technology (ICT) is largely exploited in public administration (PA). Succeeding in this exploitation calls for large-scale planning which embraces issues from strategic to technological level. In this planning the notion of enterprise architecture (EA) is commonly applied. One of the sub-architectures of EA is business architecture (BA). BA planning is challenging in PA due to a large number of stakeholders, a wide set of customers, and solid and hierarchical structures of organizations. To support …
An expert system hybrid architecture to support experiment management
2014
Specific expert systems are used for supporting, speeding-up and adding precision to in silico experimentation in many domains. In particular, many experimentalists exhibit a growing interest in workflow management systems for making a pipeline of experiments. Unfortunately, these type of systems does not integrate a systematic approach or a support component for the workflow composition/reuse. For this reason, in this paper we propose a knowledge-based hybrid architecture for designing expert systems that are able to support experiment management. This architecture defines a reference cognitive space and a proper ontology that describe the state of a problem by means of three different per…
Toward a Reference Architecture for Archival Systems
2013
Long-term preservation of product data is imperative for many organizations. A product data archive should be designed to ensure information accessibility and understanding over time. Approaches such as the Open Archival Information System (OAIS) Reference Model and the Audit and Certification of Trustworthy Digital Repositories (ACTDR) provide a framework for conceptually describing and evaluating archives. These approaches are generic and do not focus on particular contexts or content types. Enterprise architecture provides a way to describe systems in their potentially complex environments.